docs: sync README + AGENTS after v0.1.1#23
Merged
brettdavies merged 3 commits intodevfrom Apr 21, 2026
Merged
Conversation
- README: refresh sample dogfood output (26 pass / 2 warn matches current state; was 20 pass / 8 warn pre-v0.1.1 P1 gate fix). - AGENTS: 'Adding a New Check' now calls out the `covers()` declaration and the coverage-matrix regeneration step that landed in v0.1.1. Project Structure lists `src/principles/registry.rs` and `src/principles/matrix.rs`. Cross-references CLAUDE.md for the full registry conventions.
The JSON example showed a v1.0 scorecard shape (no schema_version, no coverage_summary, stale summary counts). Refreshed to match what anc actually emits in v0.1.1: - Add `schema_version: "1.1"` at top level. - Add `coverage_summary` block with MUST/SHOULD/MAY × total/verified counts against the spec registry. - Refresh summary counts (26 pass / 2 warn) to match post-P1-gate-fix behaviour. - Document `audience` and `audit_profile` as reserved v0.1.3 fields with a feature-detection note for consumers. Same PR as the README sample output + AGENTS covers() update. Both sweeps target v0.1.1 surface area.
Seven issue templates landed in v0.1.1 (false-positive, scoring-bug, feature-request, grade-a-cli, pressure-test, spec-question, plus a chooser). README had no discoverability into them — folks filing issues would default to a blank 'Something else' form. Added a short 'Reporting issues' subsection under Contributing that links to /issues/new/choose and tabulates when to reach for each template. Keeps the routing context front-loaded where users actually look for it.
brettdavies
added a commit
that referenced
this pull request
Apr 21, 2026
## Summary Release branch for v0.1.2. Cherry-picked from `dev`: - **PR #24** — v0.1.2 feature: 3 new behavioral checks (`p1-flag-existence`, `p1-env-hints`, `p6-no-pager-behavioral`) + shared `HelpOutput` cache + `Confidence` field on `CheckResult` + `dual_layer` stat in coverage matrix + `main` ruleset review count 0 → 1. - **PR #23** — post-v0.1.1 README + AGENTS sync that never made it into the v0.1.1 release branch. Plus the standard release-branch mechanics: `Cargo.toml` bump to `0.1.2`, `Cargo.lock` refresh, regenerated `CHANGELOG.md` (git-cliff from squash-commit `## Changelog` bodies). Completions had no drift this cycle — CLI surface unchanged. ## Type of Change - [x] `feat`: new user-visible capabilities (three behavioral checks + `confidence` field + dual-layer coverage stat) ## Testing - [x] All tests passing on dev head before cherry-pick (41 / 41) - [x] Pre-push hook green on release branch: fmt / clippy `-Dwarnings` / test / cargo-deny / Windows compat - [x] Coverage matrix drift check passes against the committed artifacts - [x] Smoke-tested against `rg` / `bat` / `bird` / `xr` / `anc` itself ## Files Modified See the two cherry-pick bodies (commits `72ca148` and `2fcb08d`) plus `CHANGELOG.md` + `Cargo.toml` + `Cargo.lock` for the release mechanics. ## Deployment Notes Post-merge: 1. Annotated tag + push — `git tag -a -m "Release v0.1.2" v0.1.2 && git push origin main --tags`. 2. Tag push triggers `release.yml` → `cargo publish` (Trusted Publishing) → GitHub Release (draftless, `make_latest: false` during bottle window) → Homebrew dispatch → `finalize-release` flips `make_latest: true`. 3. Follow-on on `agentnative-site`: install v0.1.2, regenerate the 10 committed scorecards (H3's proven workflow), run `scripts/sync-coverage-matrix.sh` to pull `dual_layer: 7` into `src/data/coverage-matrix.json`. ## Breaking Changes - [x] No breaking changes. Scorecard schema stays at `1.1`; `confidence` on results and `dual_layer` on matrix summary are additive. ## Checklist - [x] CI-equivalent gates green locally - [x] Cherry-picks touched no guarded paths (`docs/plans/`, `docs/solutions/`, `docs/brainstorms/`, `docs/reviews/`) - [x] `Cargo.toml` version matches the tag this branch will produce - [x] CHANGELOG entries reflect user-facing changes only
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Small post-release doc sync against what actually shipped in v0.1.1.
Not tied to the next release — lands on `dev` for the next release
branch to cherry-pick whenever it cuts.
Two files touched:
`README.md` — refreshed the sample dogfood output. The block at
line 82 showed `30 checks: 20 pass, 8 warn, 0 fail, 2 skip, 0 error`,
which was accurate pre-v0.1.1. After the P1 applicability gate fix
landed, current state is `30 checks: 26 pass, 2 warn, 0 fail, 2 skip,
0 error`. Just the sample output; check count and structure unchanged.
`AGENTS.md` — closed a real drift. The "Adding a New Check"
section listed the `Check` trait methods as `id()`, `group()`,
`layer()`, `applicable()`, `run()` — missing `covers()` which
landed in v0.1.1. New contributors adding a check without `covers()`
would silently not appear in the coverage matrix. Also added the
`cargo run -- generate coverage-matrix` regeneration step. Project
Structure list gained `src/principles/registry.rs` and
`src/principles/matrix.rs`. Cross-references CLAUDE.md for the full
conventions (registry rules, drift detector, artifact lifecycle).
Changelog
Documentation
regeneration step in the "Adding a New Check" guide.
Type of Change
Related
`covers()`, `src/principles/registry.rs`, and `anc generate coverage-matrix`.
this PR just makes AGENTS.md point at them so contributors hit it from the right entry doc.
Testing
Files Modified